Installed System Software

These Inspectors help you manage system objects and software packages.

rpmdatabase

The <rpmdatabase> objects are the Linux RPM Package Manager Inspectors. The RPM database contains entries for all the installed programs on this computer.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

package

This filesystem object can inspect the propeties of an RPM (RPM Package Manager) package. Each package contains information about the program, including name and version.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

capability

A package can have capabilities that it requires, provides, obsoletes, or conflicts with. For instance, apache may require sh, and provide httpd. If you want to install apache, you will need to have sh in the RPM database. If you want to install a package that uses httpd, you will need to install apache.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package release

The <rpm package release> Inspectors disclose properties of the RPM package version record Inspector. They are collected from the 'Release' component of the Epoch, Version and Release fields associated with an RPM package. The behavior of this inspector differs from a string, because they are sorted according to RPM rules defined by the rpmvercmp() function of the RPM library. Don't create an <rpm package release> inspector with embedded '-' or whitespace characters. These characters are disallowed in RPM, and will cause the statement to fail. Note: Requires the presence of the RPM library and librpminfo (an open source library created by BigFix containing modified RPM library code) on the client machine. librpminfo is installed on the client as part of the normal BES client RPM installation procedure.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package release with multiplicity

The <rpm package release with multiplicity> Inspectors deal with arrays of RPM package releases, allowing you to extract unique releases and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package version

The <rpm package version> Inspectors disclose properties of the RPM package version record Inspector. They are collected from the 'Version' component of the Epoch, Version and Release fields associated with an RPM package. The behavior of this inspector differs from a string, because they are sorted according to RPM rules defined by the rpmvercmp() function of the RPM library. Don't create an <rpm package release> inspector with embedded '-' or whitespace characters. These characters are disallowed in RPM, and will cause the statement to fail. Note: Requires the presence of the RPM library and librpminfo (an open source library created by BigFix containing modified RPM library code) on the client machine. librpminfo is installed on the client as part of the normal BES client RPM installation procedure.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package version with multiplicity

The <rpm package version with multiplicity> Inspectors deal with arrays of RPM package versions, allowing you to extract unique versions and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package version record

The <rpm package version record> Inspectors provide version-related information, such as Epoch, Version and Release, for an RPM package. Inspectors of this type are sorted according to an RPM-specific ordering mechanism defined by the rpmVersionCompare() function of the RPM library.Note: Requires the presence of the RPM library and librpminfo (an open source library created by BigFix containing modified RPM library code) on the client machine. librpminfo is installed on the client as part of the normal BES client RPM installation procedure.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

rpm package version record with multiplicity

The <rpm package version record with multiplicity> Inspectors deal with arrays of RPM package version records, allowing you to extract unique records and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

short rpm package version record

This is the same as an RPM package version record, except that the epoch (if one exists) is not shown when converted to a string. However, even though it isn't displayed, the epoch is still retained. If you need to remove the epoch, use one of the 'no epoch' Inspectors.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

short rpm package version record with multiplicity

The <short rpm package version record with multiplicity> Inspectors deal with arrays of short RPM package version records, allowing you to extract unique records and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

pkgdb

This is a database object created by BigFix to keep track of all the Solaris packages (pkginfos) that have been installed on this computer. The pkginfo object, in turn, contains Solaris patches, each with an ID and a revision number. The database essentially contains a comprehensive list of patches, allowing you to directly access a patch without going through pkginfo. The syntax is "patch of pkgdb", which can greatly simplify your relevance expressions.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

pkginfo

Pkginfo is an object containing information about Solaris packages, which are used to deliver patches. Pkginfo contains information about the category, the intended architecture, vendors, patch IDs and revision numbers. Other package information can be inspected using the "param" property which lets you access other parameters by name.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

patch

An object that exposes the properties of a Solaris patch, each of which has a base ID followed by a revision number, such as 123456-12. Here the base is 123456, which identifies the patch, and 12, which represents the revision of this particular patch.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

bundle

On HPUX platforms, a bundle object is derived from a product type and used to inspect software installations as managed by the Software Depot. On Macintosh platforms, a bundle refers to a core foundation folder hierarchy derived from CFBundle.

Creation Methods

Declaration	Description	Platforms (?)
bundle <string>	Returns a bundle (CFBundle) by name. Example: bundle "com.apple.BigFixEnterprise" - Returns a bundle to hand to something that needs one. It doesn't print out, per se.	Mac
bundle of <folder>	Returns a bundle from a folder (if it has one like application folders do). Example: exists (bundle of applications folder) - Typically returns TRUE.	Mac

Properties

Declaration	Return type	Description	Platforms (?)
bundle version of <bundle>	<version> Plural: bundle versions	Returns the version of the bundle corresponding to the CFBundleVersion string, as distinct from the CFBundleShortVersionString.	Mac
creator of <bundle>	<file signature> Plural: creators	The creator 4-letter code of the bundle (for example, FNDR for Finder).	Mac
global dictionary of <bundle>	<dictionary> Plural: global dictionaries	The bundle's information dictionary.	Mac
local dictionary of <bundle>	<dictionary> Plural: local dictionaries	The bundle's localized information dictionary.	Mac
type of <bundle>	<file type> Plural: types	Returns the file type of the bundle. Can be used only to compare equality between file types.	Mac
version of <bundle>	<version> Plural: versions	Version of the given bundle.	Mac

product

The <product> object contains properties (such as vendor and revision) of the associated software product. On AIX, products are installed into an Object Repository.On HPUX products are installed in the Software Depot.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

object_repository

A database corresponding to installable software products on AIX computers.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

software_depot

Software Depot uses the swlist INDEX to identify the collection of products installed on the HPUX machine.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian base package

For Tivoli Inspectors, a Debian package is considered to include both the package and the version. This allows the Inspectors to home in on specific versioned packages and not just the package itself, which may have numerous versions. The base package Inspectors help to tease these two aspects apart, stripping the version info and returning a list of the packages by name only.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package upstream version with multiplicity

The <debian package upstream version with multiplicity> Inspectors deal with arrays of Debian packages, allowing you to extract unique upstream_versions and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package upstream version

The upstream_version of a Debian package is the main version number. Along with the epoch and revision, it is one of the components of the Debian versioning scheme.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version epoch with multiplicity

The <debian package version epoch with multiplicity> Inspectors deal with arrays of Debian packages, allowing you to extract unique version 'epochs' and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version epoch

The <debian package version epoch> Inspectors deal with the 'epoch' component of a Debian package version. The epoch is an unsigned integer, typically a small number. If it is omitted, zero is the default. It allows the package provider to create a fresh start with version numbering schemes.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version revision with multiplicity

The <debian package version revision with multiplicity> Inspectors deal with arrays of Debian package allowing you to extract unique version revisions and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version revision

Also known as the 'debian_revision', these Inspectors reveal the revision of a Debian package based on the upstream_version. The revision component of the version is optional. Typically, the revision is set to 1 whenever the upstream_version is increased.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version with multiplicity

The <debian package version with multiplicity> Inspectors deal with arrays of Debian packages, allowing you to extract unique versions and count them.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian package version

For Tivoli Inspectors, a Debian package is considered to include both the package and the version. This allows the Inspectors to home in on specific versioned packages and not just the package itself, which may have numerous versions. These version Inspectors return just the version(s) of a given Debian package. A version is composed of three parts: an epoch, an upstream_version and a debian_revision.

Creation Methods

Declaration

Description

Platforms (?)

Operators

Declaration

Return Type

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debian versioned package

The <debian versioned package> Inspectors return all the versions of the Debian package that are available for the base package.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debianpackagecache

The <debianpackagecache> Inspectors refer to the cache directory set up for Debian packages.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debianpkg dependency

A package may depend on the previous installation of other software packages. The <debianpkg dependency> Inspectors detail those dependencies. A Debian package may replace another package, conflict with it or depend on it. For more information, see the Debian.org site.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debianpkg reverse dependencies

Debian packages often depend on other packages, with you can find by looking in the given package. You can reverse the situation and instead use the Advanced Packageing Tool (APT) to discover which programs are dependent on a given package. These Inspectors allow you to find these reverse dependencies.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debianpkg verfile

The pkg Inspectors deal with base packages, i.e., packages stripped of their version information. This set of Inspectors lists the names of the APT system files that describe the package in question. If you edit and search the files that result from this inspector, you can find descriptive information about the specified packages.

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

debianpkg version

The pkg Inspectors deal with base packages, i.e., packages stripped of their version information. This set of Inspectors deals with the versions corresponding to the given package(s).

Creation Methods

Declaration

Description

Platforms (?)

Properties

Declaration

Return type

Description

Platforms (?)

Terminology

Platform

Contents